Skip to content

Version Packages - #208

Merged
SandroMaglione merged 1 commit into
mainfrom
changeset-release/main
Sep 6, 2026
Merged

Version Packages#208
SandroMaglione merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@typeonce/effect-machine@0.33.0

Minor Changes

  • 3255f24: Construct atomic destination and retained-owner updates with .updating(owner).from(({ current, event }) => ({ target, update })), or use .decoded(...) for decoded values. Both values are complete replacements; .resolve(...) remains available for explicit configuration builders and commands. Value updates and atomic transitions now support .guard(...), declining before construction and commands while preserving ancestor fallback.

    Use chainable .reenter() before .from(...), .decoded(...), or .resolve(...) to force source exit and entry. Replace .resolve(callback, { reenter: true }) with .reenter().resolve(callback) and omit reentry entirely when it is false. Named branching transitions use .branches(...).reenter().resolve(...). The redundant-resolver lint rule preserves these modifiers when simplifying default construction.

@typeonce/effect-machine-devtools@0.33.0

Patch Changes

  • Updated dependencies [3255f24]
    • @typeonce/effect-machine@0.33.0

@typeonce/effect-machine-react@0.33.0

Patch Changes

  • Updated dependencies [3255f24]
    • @typeonce/effect-machine@0.33.0

@typeonce/oxlint-plugin-effect-machine@0.33.0

Patch Changes

  • 3255f24: Construct atomic destination and retained-owner updates with .updating(owner).from(({ current, event }) => ({ target, update })), or use .decoded(...) for decoded values. Both values are complete replacements; .resolve(...) remains available for explicit configuration builders and commands. Value updates and atomic transitions now support .guard(...), declining before construction and commands while preserving ancestor fallback.

    Use chainable .reenter() before .from(...), .decoded(...), or .resolve(...) to force source exit and entry. Replace .resolve(callback, { reenter: true }) with .reenter().resolve(callback) and omit reentry entirely when it is false. Named branching transitions use .branches(...).reenter().resolve(...). The redundant-resolver lint rule preserves these modifiers when simplifying default construction.

@SandroMaglione
SandroMaglione merged commit 9b03a33 into main Sep 6, 2026
8 checks passed
@SandroMaglione
SandroMaglione deleted the changeset-release/main branch September 6, 2026 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant